ci: release-please + jar release pipeline#10
Merged
Conversation
- release-please-config.json: simple type, bump-minor-pre-major, release-as 0.1.0 (first release goes to 0.1.0 not 1.0.0) - .release-please-manifest.json seeded at 0.0.0 - .github/workflows/release-please.yml: shared groundsgg/.github release-please reusable workflow - .github/workflows/release.yml: custom — on tag push, builds the shadow JAR with the tag's version and uploads it to the GH release via gh CLI Deviation from shared gradle-publish.yml: that workflow expects a `./gradlew publish` task wired through maven-publish. We don't consume this plugin as a Gradle dependency anywhere, so the maven-publish overhead is not warranted; the Velocity-plugin shadow JAR is the distributable. Custom Velocity image (spec §4.3) is intentionally deferred to a follow-up — v0.1 ships JAR-only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
release-please-config.json— simple release-type,bump-minor-pre-major,release-as: 0.1.0so the first auto-release lands on 0.1.0 (not 1.0.0).release-please-manifest.jsonseeded at 0.0.0.github/workflows/release-please.yml— uses the sharedgroundsgg/.githubreusable workflow.github/workflows/release.yml— custom: on tag push, builds the shadow JAR with the tag's version and uploads to the GH release viagh release uploadWhy custom release.yml (not shared gradle-publish.yml)
The shared
gradle-publish.ymlruns./gradlew publishagainst a Maven publication. This plugin isn't consumed as a Gradle dependency anywhere, so the maven-publish overhead is not warranted; the Velocity-plugin shadow JAR is the distributable.Deferred to a follow-up
Custom Velocity image bundling the JAR + prod plugins (spec §4.3) — v0.1 ships JAR-only.
Test plan
./gradlew shadowJarproduces the artifact locallyPlan: docs/plans/2026-04-25-plugin-platform-router.md (T10)